home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
opendoor.zip
/
OPENDOOR.DOC
< prev
next >
Wrap
Text File
|
1988-12-25
|
11KB
|
265 lines
O P E N D O O R
Release 1.0 in January 89
Written by Fast Fingers ...
The Sysop of the Tool Box BBS
Sterling Heights, Michigan
Phone # (313)-247-0094
SYSOP DOCUMENTATION for the OPENDOOR door utility BBS interface package.
*** INTRODUCTION ***
I am frequently accused of supplying a two pound answer for a 3 ounce
question. While the operation of this program is simple I have included
enough information here for you to really understand what's going on. I
do this because many sysop's call my system somewhat confused by setting
up doors and the whole process is frustrating when a great game, "door",
can not be brought up on a system after quite an effort to get the program
in the first place was expended.
*** DELIVERABLES ***
The package as you received it should have included the following files:
OPENDR10.ARC
OpenDoor.Doc ... This file.
OpenDoor.Exe ... The compiled version of release 1.0.
OpenDoor.Def ... An example configuration file for this program.
OpenDoor.Bas ... The Quick Basic 4.0 source code.
*** GENERAL PURPOSE ***
Many sysop's have trouble installing door programs written for bbs systems
different from what they are using. On the other side of the issue are
the authors of door programs that really don't care about the variety of
bbs systems and simply want sysops to be able to use their programs easily.
As I upgrade my various Ansi graphics/windowing doors I am removing all
bbs dependant logic from them. However, they still do need to know some
basic information unique to each caller/bbs system, such as:
The Users first name ...................... Joe
The Users last name ....................... Blow
The Current Communication parameters ...... COM1:2400,N,8,1
The Time left for BBS session ............. 32
*** OPERATION ***
Fundamentally, OpenDoor.Exe is a program designed to reside in the same
directory as the BBS. It merges the information needed, described above,
with information in the File "OPENDOOR.DEF" to create a file it puts in
the same directory as the door called "OPENDOOR.SYS". It accomplishes
this task by having a bbs data dependant driver for each kind of BBS it
has been taught to understand. As such, if your BBS type is not supported
by this program, and you are a little handy with QB4.0, you can add a new
subroutine that can extract the required information and all of the ansi
doors will now work with your type of BBS.
*** OPENDOOR.DEF ***
The information merged with the user's unique parameters are stored in
the file called "OPENDOOR.DEF" and this file looks like this:
The Tool Box
Fast
Fingers
COM1:
PCBOARD.SYS
55
OFF
Line #1 The Name of the BBS ....................... The Tool Box
Line #2 The Sysop's first name .................... Fast
Line #3 The Sysop's last name ..................... Fingers
Line #4 The Default Com Port ...................... COM1:
Line #5 The Name of the BBS.SYS info file ......... PCBOARD.SYS
Line #6 The Maximum minutes allowed in door ....... 55
Line #7 The Debug Status of Door Operation ........ OFF
Note: There can NOT be any ","'s in this file and the communications
port being used must be fully qualified as "COM1:" or "COM2:".
This file must be located in the same directory as the BBS and
the "OPENDOOR.EXE" program.
*** OPENDOOR.SYS ***
The merged result, "OPENDOOR.SYS" for the combined examples above would
look like the following:
The Tool Box
Fast
Fingers
COM1:2400,N,8,1
Joe
Blow
32
OFF
This file will be created in the same directory as the door being run.
*** PCBOARD.SYS ***
In the example above the "OPENDOOR.EXE" program assumed that a file
describing the user's situation existed in the BBS directory and it was
named "PCBOARD.SYS". This file would look like the following:
-1 0 0 0 2400JOE BLOW JOE -1PASSWORD----
æ
æ19:47
Don't let this confuse you as interpretation is the purpose of this code.
Note however, that "OPENDOOR.EXE" will return, rather than call a door if
the user does NOT have ansi graphics enabled, NOT connected with no parity,
NOT using 8 data bits and 1 stop bit.
*** DATA FLOW SUMMARY ***
****************
******* *************** * *
* BBS *===>* PCBOARD.SYS *===>* *
******* *************** * OPENDOOR.EXE * ****************
: * *===>* OPENDOOR.SYS *
: **************** * * ****************
: * OPENDOOR.DEF *===>* * :
: **************** * * ************ *********
: * *===>* DOOR.EXE *===>* MODEM *
************ Arguments=> * * ************ *********
* DOOR.BAT *====================>* * :
************ * * ************
**************** * DOOR.DEF *
************
USER => BBS => DOOR.BAT => OPENDOOR.EXE => DOOR.EXE => MODEM => USER
*** OPENDOOR.EXE (ARGUMENTS) ***
The batch file that you set up to call "OPENDOOR.EXE" MUST supply the code
with at least one input parameter. If you call it without any arguments
it assumes you are simply setting it up and it goes into instruction mode
operation giving you some help information on how to run it.
The required argument, first one, is the fully qualified "Drive+Path+Door".
For example the statement could look like:
OPENDOOR.EXE D:\TAG\GAMES\CHECKERS\CHECKERS.EXE
The second, optional, argument if supplied assumes you want to run the
door in local mode. An example of this batch or dos command would be:
OPENDOOR.EXE D:\TAG\GAMES\CHECKERS\CHECKERS.EXE LOCAL
Note: After a caller has accessed your door the only way to run it locally
again is either the above example or changing to the door directory,
deleting the opendoor.sys file and then keying in the name of the
door.
*** BBS SYSTEMS SUPPORTED ***
As of this release the def file, Line #5, can be one of two settings. One
is "PCBOARD.SYS" and the other is "DORINFO1.DEF". The previous examples
all assumed the pcboard option. RBBS and some of bulletin board systems
now support "DORINFO1.DEF". While the information here is formatted its
own unique way the process is the same and the only change from your point
of view is the change to the one line in the opendoor.def file that
signals a different conversion is required.
*** ADDING ADDITIONAL BBS SUPPORT ***
This same input, opendoor.def ... Line #5, is what you would change if
you decide to write a different bbs door driver subroutine. In this case
don't worry about compiling the program with the DTR patches as this
program does not try to communicate over the modem. If you do take this
path please study the driver for the pcboard.sys and follow the same type
procedures. For example, the ansi doors do not support user names with
strange characters like "." included in them. It strips these out. So a
user with a bbs name "Superman .", where "." is the last name, will have
his/her named changed by opendoor to "Mr Superman". This will allow the
doors to use the users name to determine the name of door data files
unique to the caller to save his game information.
In general I am a strong supporter of self documenting programs. You
will notice that I have left what most would consider an excessive
amount of REM statements in the code for the purpose of making any
enhancements at a later time easy.
*** OTHER DETAILS ***
Some systems do not supply information you may wish, like the com port id.
Others do not supply the time left on the bbs. These items are included
in the opendoor.def file so that the appropriate defaults may be used if
the info needed can not be obtained from the bbs.
If you do write your own drivers, without changing the input/output to the
driver routines, please send them this way. Over time I expect to upgrade
this utility to support a wide range of bulletin board systems.
Make a batch file that calls OPENDOOR.EXE, mine looks something like
the following:
ECHO TAG Batch file CHECKERS.BAT for checkers door
D:
CD \TAG
REM
REM Now call quickdor to convert TAG communications output
REM into a pcboard.sys format
REM
QUICKDOR %4,%5,%1,%6,%2,%3
REM
REM Now call opendoor configured for PCBOARD.SYS input
REM in its file named OPENDOOR.DEF
REM
D:\TAG\OPENDOOR.EXE D:\TAG\GAMES\CHECKERS\CHECKERS.EXE
REM
ECHO DOOR CLOSED
D:
CD \TAG
Note: You notice that I didn't call watchdog as all of my doors
monitor the connection with the user themselves. The QuickDor
line is unique to TAG. If for example you were running a
RBBS system that outputs a DORINFO1.DEF file all you would need
is to setup the opendoor.def file correctly once and then have
a batch file with the single line:
OPENDOOR.EXE C:\RBBS\DOORS\CHECKERS.EXE
Now do whatever it takes on your BBS to let it know you have another
great ansi-graphics door from Fast Fingers.
*** CLOSING CREDITS ***
While I'm thinking of it, if you find this program useful take $50 of
your hard earned money and take your special somebody out on the town.
Tell them its on Fast Fingers! There are no restrictions on anybody at
anytime or anyplace as to how they may use and/or modify this program.
I would however appreciate it if some reference to the original author
is left intact for my ego's reward for the effort expended to bring this
package into existence. Thanks for taking the time to read all this
mostly unnecessary information. I hope you enjoy it. Have a good one!
Enjoy!
Fast Fingers ....
ps: Give my system a call some time and treat yourself to one of the
best BBS systems in the Midwest!